Skip to content

Add optional publisher policy URLs to the plugin manifest - #96

Open
digitarald wants to merge 1 commit into
mainfrom
agent/policy-urls
Open

digitarald wants to merge 1 commit into
mainfrom
agent/policy-urls

Conversation

@digitarald

@digitarald digitarald commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

This PR adds optional privacyPolicyUrl and termsOfServiceUrl fields to plugin.json in Agent Plugins 1.1.0, so a plugin author can declare the publisher's policies once instead of through a client-specific extension.

Motivation

The manifest carries portable publisher metadata such as homepage, repository, and license, but has no field for a privacy policy or terms of service. Both are commonly required when plugins are distributed through marketplaces or enterprise catalogs, and the information is not client-specific: it describes the plugin as distributed, regardless of which client loads it.

Authors already publish these URLs in spec-conformant manifests by placing them in a client namespace. In obsidianmd/obsidian-skills, reactive-resume, and pascalorg/editor, the manifest declares agent-plugins.org/schemas/1.0.0 and carries the policy URLs under extensions["com.openai"].interface. Clients that read a different namespace cannot see them. Cursor and Kiro both load spec-conformant plugins and define no equivalent fields of their own, so their users have nowhere portable to put this today.

The field names already exist in native manifests. Claude Code reads privacyPolicyUrl and termsOfServiceUrl from the top level of its plugin manifest, as in docker/skills. Codex reads privacyPolicyURL and termsOfServiceURL from its own interface object.

Proposal

{
  "$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
  "name": "example-plugin",
  "privacyPolicyUrl": "https://example.com/privacy",
  "termsOfServiceUrl": "https://example.com/terms"
}

The fields identify the publisher's own privacy policy and terms of service, and do not describe independently operated services that a plugin accesses. Clients may present them and are not required to retrieve or display them. A client that presents them attributes them to the plugin publisher. HTTPS is recommended.

The names follow the top-level form Claude Code already reads, which is also the casing used in the wider plugin ecosystem. No alias is defined for Codex's nested, differently cased fields, which remain part of that client's own namespace.

Rationale

Like the other metadata URLs, both fields are validated only by their JSON type. Requiring a URL form or an HTTPS scheme would make a malformed policy link fatal to an otherwise valid plugin, which is a worse outcome than a link a client can decline to present. A wrong JSON type remains fatal, as for every other recognized field.

Attributing the URLs to the publisher keeps their scope accurate without requiring a client to verify legal documents or identify who operates a service a plugin reaches.

This PR defines no relationship between the portable fields and any client namespace that carries similar data. Each client continues to own the contents and interpretation of its own extension namespace.

Compatibility

The change applies only to the 1.1.0 working draft; the published 1.0.0 specification remains unchanged. The fields are optional and additive, so existing conforming manifests stay valid and clients that do not implement them are unaffected.


Closes #92.

A plugin's privacy policy and terms of service describe the plugin as
distributed rather than the client that loads it, so clients and catalogs
otherwise rediscover the same information through client-specific
extensions. Add optional `privacyPolicyUrl` and `termsOfServiceUrl` fields
to the plugin manifest so an author can declare them once.

Both fields are validated only by their JSON types, matching the treatment
of `homepage`, `repository`, and `author.url`: a malformed policy link is
not fatal to an otherwise valid plugin. HTTPS is recommended, not required.

Clients may present the URLs and are not required to retrieve or display
them. A client that presents them attributes them to the plugin publisher,
since the fields do not describe independently operated services that a
plugin accesses.

Closes #92

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@digitarald digitarald closed this Nov 13, 2026
@digitarald digitarald reopened this Nov 13, 2026
@jonathanhefner jonathanhefner added this to the v1.1.0 milestone Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add optional privacyPolicyUrl and termsOfServiceUrl to plugin metadata

2 participants